The Recipe Scraper API is a powerful tool for anyone looking to collect recipe information from the web. This API allows users to extract recipe information from a provided URL, allowing them to access the recipe's title, ingredients, instructions, and other relevant information. The API returns the data in a structured format, such as JSON, making it easy to parse and display in a user-friendly format.
This API can be integrated into a variety of applications, such as recipe apps, meal planning, and food-related projects. For example, in a recipe app, users can input a recipe URL and the API will extract the recipe's title, ingredients, and instructions, allowing the user to view and save the recipe. Similarly, in meal planning applications, the API can be used to collect recipes from various websites and present them in a structured format for the user to select from.
The API supports multiple languages, so you can use it for different regions and cultures. It also has a feature to extract recipe images, so you can use it for recipe visualization, for example.
In summary, the Recipe Scraper API is a valuable tool for anyone in the food industry. It allows users to extract recipe information from a provided URL, providing access to the recipe's title, ingredients, instructions, and other relevant information. It can be integrated into a variety of applications, such as recipe apps, meal planning, and food-related projects. It's easy to use and returns data in a structured format, and supports multiple languages and image extraction.
Pass an URL that contains a recipe to the API. The API will scrape the content and will deliver the information in a structured JSON.
Recipe Applications: Users can input a recipe URL and the API will extract the recipe's title, ingredients, and instructions, allowing the user to view and save the recipe.
Meal Planning Applications: The API can be used to collect recipes from various websites and present them in a structured format for the user to select from.
Food Blogs and Websites: Extract recipe information from food blogs and websites to create a recipe database or to feature recipes on a website.
Cooking and Recipe Books Digitalization: Extract recipe information from scanned cooking and recipe books to create a digital recipe database.
Recipe Analysis and Nutritional Information: Extract recipe information from the web to analyze the recipe ingredients and provide nutritional information.
Recipe Search Engine: Use the API to extract recipe information from various websites and use it to power a recipe search engine.
Besides API call limitations per month, there are no other limitations.
Pass an URL with a recipe within it. The API will scrape the URL and retrieve the recipe in a structured JSON object.
Get Recipe from URL - Endpoint Features
Object | Description |
---|---|
url |
[Required] URL to extract the recipe from. |
{"recipe":{"name":"Best Green Bean Casserole","recipeYield":"6","recipeInstructions":["Preheat the oven to 350 degrees F (175 degrees C).","Mix green beans and condensed soup together in a large microwave-safe bowl until well combined. Microwave on high until warm, 3 to 5 minutes.","Stir 1/2 cup Cheddar cheese into the green bean mixture. Microwave on high for 2 to 3 minutes.","Transfer mixture to a casserole dish and spread evenly over the bottom. Sprinkle remaining Cheddar over top, then sprinkle with the French-fried onions.","Bake in the preheated oven until cheese is melted and the onions are just turning brown, about 10 minutes."],"recipeIngredient":["2 (14.5 ounce) cans green beans, drained","1 (10.5 ounce) can condensed cream of mushroom soup","1 cup shredded Cheddar cheese, divided","1 (6 ounce) can French-fried onions"],"nutrition":null,"description":"This green bean casserole pairs tender green beans with crunchy French-fried onions in creamy cheese sauce. A family-favorite recipe for the holidays!","prepTime":"PT10M","cookTime":"PT15M","totalTime":"PT25M","image":"https://www.allrecipes.com/thmb/UfNSt8UMs3xmOgRjmwqAnGl_Oz4=/1500x0/filters:no_upscale():max_bytes(150000):strip_icc()/418379-best-green-bean-casserole-mfs_108-1-748e6c55722a44039c10f06347f2b2a1.jpg","datePublished":"2000-06-07T16:59:05.000-04:00","dateModified":"2024-08-14T15:55:40.182-04:00"},"status":"success","error":null,"error_message":null}
curl --location --request GET 'https://zylalabs.com/api/935/recipe+scraper+api/753/get+recipe+from+url?url=https://cookieandkate.com/margherita-pizza-recipe/' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
65%
Response Time:
748ms
Service Level:
100%
Response Time:
575ms
Service Level:
100%
Response Time:
1,043ms
Service Level:
100%
Response Time:
3,080ms
Service Level:
100%
Response Time:
548ms
Service Level:
100%
Response Time:
638ms
Service Level:
100%
Response Time:
684ms
Service Level:
96%
Response Time:
6,534ms
Service Level:
100%
Response Time:
4,932ms
Service Level:
65%
Response Time:
8,056ms
Service Level:
79%
Response Time:
1,883ms
Service Level:
100%
Response Time:
898ms
Service Level:
100%
Response Time:
982ms
Service Level:
100%
Response Time:
5,883ms
Service Level:
100%
Response Time:
6,283ms
Service Level:
100%
Response Time:
811ms
Service Level:
100%
Response Time:
599ms